Repository navigation
feat(docker): reuse build digests and skip redundant setup - #953
Conversation
|
Internal - Pull request - Continuous Integration - Test results Workflow run and full reports · Commit 529bf07 Jobs: 2 success · 0 failure · 0 cancelled · 0 skipped · 0 abandoned. Test: 14 passed · 0 failed · 0 skipped. Test detailsTest resultsTest Results
Job results and report availability
Only this attempt is included. On partial reruns, rerun all producer jobs for complete reports. CodeQL findings remain in code scanning; other diagnostics remain in the job logs. |
|
Internal - Pull request - Continuous Integration - Code coverage Workflow run and full reports · Commit 529bf07 Jobs: 2 success · 0 failure · 0 cancelled · 0 skipped · 0 abandoned. Coverage: 1 source report(s); percentages remain separate. Coverage detailsCoverage resultsCoverage
Overall: 100.00% 🟢 Job results and report availability
Only this attempt is included. On partial reruns, rerun all producer jobs for complete reports. CodeQL findings remain in code scanning; other diagnostics remain in the job logs. |
|
Internal - Pull request - Continuous Integration - Lint results Workflow run and full reports · Commit 529bf07 Jobs: 2 success · 0 failure · 0 cancelled · 0 skipped · 0 abandoned. Lint: Collected diagnostics and Super-Linter summaries. Execution status is included in the job outcomes. Super-Linter detailsSuper-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter Job results and report availability
Only this attempt is included. On partial reruns, rerun all producer jobs for complete reports. CodeQL findings remain in code scanning; other diagnostics remain in the job logs. |
Single-platform builds already publish their tags and return an immutable digest. Publication currently discards that digest, initializes Docker/Buildx and resolves the tags again; attestation also initializes Docker only to authenticate to the registry.
This change reuses validated single-platform source digests and adds
setup-docker: falseto the existing setup action. Publication skips Docker/Buildx setup when every image has a reusable digest. Attestation uses registry authentication only. Runners with an existing Docker CLI avoid daemon setup; runners without the CLI retain the installation fallback. Tag-only inputs, multi-platform assembly and explicit tag cloning retain their inspection path. Malformed tags and conflicting digest metadata fail before publication.Registry credentials, cosign signing, provenance subjects and build-job permissions remain intact. The publication job no longer requests unused attestation-write permission. No cache or DAG changes are included.
Implements P2.3 of Pleey's CI optimization plan, following review of Pleey #553.
Validation:
Initial candidate action medians across the platform/signing matrix: single-platform publication 19.5s → 1s; attestation registry setup 12.5s → 1s. Multi-platform publication remains approximately unchanged (23s → 23.5s). These compare a previous main run with the initial candidate run, not controlled repeated benchmarks or Pleey end-to-end measurements. The final revision also passed: its observed medians were 1s for single-platform publication and 1.5s for attestation setup.
The ADR records ranges, whole-job/cleanup timings, compatibility and limitations. Downstream adoption follows upstream review and release.